Relay Reception Synchronization System and Method

ABSTRACT

A method for informing a relay node when to receive data. The method includes the relay node being informed of a fixed point in a subframe of data when an access node will begin transmitting relevant data over a physical downlink shared channel. The method further includes the relay node beginning to receive data at approximately the fixed point.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims priority to U.S. Provisional Patent Application No. 61/160,158, filed Mar. 13, 2009, by Yi Yu, et al, entitled “Relay Reception Synchronization System and Method” (35130-US-PRV-4214-15900); U.S. Provisional Patent Application No. 61/160,156, filed Mar. 13, 2009, by Yi Yu, et al, entitled “Relay Link Control Channel Design” (35081-US-PRV-4214-15800); and U.S. Provisional Patent Application No. 61/160,163, filed Mar. 13, 2009, by Yi Yu, et al., entitled “Resource Assignments for Relay System and Method” (35131-US-PRV-4214-16000), all of which are incorporated by reference herein as if reproduced in its entirety.

BACKGROUND

As used herein, the terms “user agent” and “UA” might in some cases refer to mobile devices such as mobile telephones, personal digital assistants, handheld or laptop computers, and similar devices that have telecommunications capabilities. Such a UA might consist of a UA and its associated removable memory module, such as but not limited to a Universal Integrated Circuit Card (UICC) that includes a Subscriber Identity Module (SIM) application, a Universal Subscriber Identity Module (USIM) application, or a Removable User Identity Module (R-UIM) application. Alternatively, such a UA might consist of the device itself without such a module. In other cases, the term “UA” might refer to devices that have similar capabilities but that are not transportable, such as desktop computers, set-top boxes, or network appliances. The term “UA” can also refer to any hardware or software component that can terminate a communication session for a user. Also, the terms “user agent,” “UA,” “user equipment,” “UE,” “user device” and “user node” might be used synonymously herein.

As telecommunications technology has evolved, more advanced network access equipment has been introduced that can provide services that were not possible previously. This network access equipment might include systems and devices that are improvements of the equivalent equipment in a traditional wireless telecommunications system. Such advanced or next generation equipment may be included in evolving wireless communications standards, such as long-term evolution (LTE). For example, an LTE system might include an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) node B (eNB), a wireless access point, or a similar component rather than a traditional base station. As used herein, the term “access node” will refer to any component of the wireless network, such as a traditional base station, a wireless access point, or an LTE eNB, that creates a geographical area of reception and transmission coverage allowing a UA or a relay node to access other components in a telecommunications system. An access node may comprise a plurality of hardware and software.

The term “access node” may not refer to a “relay node,” which is a component in a wireless network that is configured to extend or enhance the coverage created by an access node or another relay node. The access node and relay node are both radio components that may be present in a wireless communications network, and the terms “component” and “network node” may refer to an access node or relay node. It is understood that a component might operate as an access node or a relay node depending on its configuration and placement. However, a component is called a “relay node” only if it requires the wireless coverage of an access node or other relay node to access other components in a wireless communications system. Additionally, two or more relay nodes may be used serially to extend or enhance coverage created by an access node.

An LTE system can include protocols such as a Radio Resource Control (RRC) protocol, which is responsible for the assignment, configuration, and release of radio resources between a UA and a network node or other LTE equipment. The RRC protocol is described in detail in the Third Generation Partnership Project (3GPP) Technical Specification (TS) 36.331. According to the RRC protocol, the two basic RRC modes for a UA are defined as “idle mode” and “connected mode.” During the connected mode or state, the UA may exchange signals with the network and perform other related operations, while during the idle mode or state, the UA may shut down at least some of its connected mode operations. Idle and connected mode behaviors are described in detail in 3GPP TS 36.304 and TS 36.331.

The signals that carry data between UAs, relay nodes, and access nodes can have frequency, time, and coding parameters and other characteristics that might be specified by a network node. A connection between any of these elements that has a specific set of such characteristics can be referred to as a resource. The terms “resource,” “communications connection,” “channel,” and “communications link” might be used synonymously herein. A network node typically establishes a different resource for each UA or other network node with which it is communicating at any particular time.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of this disclosure, reference is now made to the following brief description, taken in connection with the accompanying drawings and detailed description, wherein like reference numerals represent like parts.

FIG. 1 is a diagram illustrating a wireless communication system that includes a relay node, according to an embodiment of the disclosure.

FIG. 2 a is a diagram illustrating an access node control region that is smaller than a corresponding relay node control region.

FIG. 2 b is a diagram illustrating an access node control region that is larger than a corresponding relay node control region.

FIG. 3 a is a diagram of a subframe of data with a fixed start point for PDSCH data according to an embodiment of the disclosure.

FIG. 3 b is a diagram of a subframe of data with a fixed start point for PDSCH data according to an alternative embodiment of the disclosure.

FIG. 4 is a block diagram of a method for informing a relay node when to receive data according to an embodiment of the disclosure.

FIG. 5 illustrates a processor and related components suitable for implementing the several embodiments of the present disclosure.

DETAILED DESCRIPTION

It should be understood at the outset that although illustrative implementations of one or more embodiments of the present disclosure are provided below, the disclosed systems and/or methods may be implemented using any number of techniques, whether currently known or in existence. The disclosure should in no way be limited to the illustrative implementations, drawings, and techniques illustrated below, including the exemplary designs and implementations illustrated and described herein, but may be modified within the scope of the appended claims along with their full scope of equivalents.

FIG. 1 is a diagram illustrating a wireless communication system 100 that includes a relay node 102, according to an embodiment of the disclosure. Examples of the wireless communication system 100 include LTE or LTE-Advanced (LTE-A) networks, and all of the disclosed and claimed embodiments could be implemented in an LTE-A network. LTE may be said to correspond to 3GPP Release 8 (Rel-8 or R8) and Release 9 (Rel-9 or R9) while LTE-A may be said to correspond to Release 10 (Rel-10 or R10) and possibly to releases beyond Release 10.

The relay node 102 can amplify or repeat a signal received from a UA 110 and cause the modified signal to be received at an access node 106. In some implementations of a relay node 102, the relay node 102 receives a signal with data from the UA 110 and then generates a new signal to transmit the data to the access node 106. The relay node 102 can also receive data from the access node 106 and deliver the data to the UA 110.

The relay node 102 might be placed near the edges of a cell so that the UA 110 can communicate with the relay node 102 rather than communicating directly with the access node 106 for that cell. In radio systems, a cell is a geographical area of reception and transmission coverage. Cells can overlap with each other. In the typical example, there is one access node associated with each cell. The size of a cell is determined by factors such as frequency band, power level, and channel conditions. Relay nodes, such as relay node 102, can be used to enhance coverage within a cell or to extend the size of coverage of a cell. Additionally, the use of a relay node 102 can enhance throughput of a signal within a cell because the UA 110 can access the relay node 102 at a higher data rate than the UA 110 might use when communicating directly with the access node 106 for that cell, thus creating higher spectrum efficiency. The use of a relay node 102 can also decrease the UA's battery usage by allowing the UA 110 to transmit at a lower power.

Relay nodes can be divided into three types: layer one relay nodes, layer two relay nodes, and layer three relay nodes. A layer one relay node is essentially a repeater that can retransmit a transmission without any modification other than amplification and slight delay. A layer two relay node can decode a transmission that it receives, re-encode the result of the decoding, and then transmit the re-encoded data. A layer three relay node can have full radio resource control capabilities and can thus function similarly to an access node. The radio resource control protocols used by a relay node may be the same as those used by an access node, and the relay node may have a unique cell identity typically used by an access node. The illustrative embodiments are primarily concerned with layer two or layer three relay nodes. Therefore, as used herein, the term “relay node” will not refer to layer one relay nodes, unless specifically stated otherwise.

When the UA 110 is communicating with the access node 106 via the relay node 102, the links that allow wireless communication can be said to be of three distinct types. The communication link between the UA 110 and the relay node 102 is said to occur over an access link 108. The communication between the relay node 102 and the access node 106 is said to occur over a relay link 104. Communication that passes directly between the UA 110 and the access node 106 without passing through the relay node 102 is said to occur over a direct link 112.

The access node 106 sends data to the relay node 102 in a series of subframes, each of which consists of a relatively shorter control region followed by a relatively longer data region. The control region, or physical downlink control channel (PDCCH), typically consists of one to four orthogonal frequency-division multiplexing (OFDM) symbols. The data region, or physical downlink shared channel (PDSCH), can be considerably longer. The relay node 102 sends data to the UA 110 in a similar format.

Under current configurations, the relay node 102 transmits control data to the UA 110 at the same time that the access node 106 is transmitting control data to the relay node 102. However, the relay node 102 typically cannot transmit and receive data at the same time. Therefore, the relay node 102 may not receive the control information that is transmitted by the access node 106 while the relay node 102 is transmitting control information to the UA 110. A portion of the control information that the access node 106 transmits might specify the size of that control information, that is, the size of the PDCCH region. Since the relay node 102 might not receive this information, the relay node 102 may not know when PDCCH data ends and PDSCH data begins. The relay node 102 simply begins listening for the PDSCH data from the access node 106 upon completing the transmission of control information to the UA 110. It is possible that the time when the relay node 102 starts to listen for PDSCH data from the access node 106 may not coincide with the time when the access node 106 starts to transmit PDSCH data. This might cause the relay node 102 to miss a portion of the PDSCH data or to listen for PDSCH data while the access node 106 is still sending PDCCH data.

FIG. 2 a illustrates one such scenario. A subframe 210 of data sent from the access node 106 to the relay node 102 consists of a PDCCH region 212 and a PDSCH region 214. Similarly, a subframe 220 of data sent from the relay node 102 to the UA 110 consists of a PDCCH region 222 and a PDSCH region 224. The PDCCH region 212 and the PDSCH region 214 in the subframe 210 sent from the access node 106 are not necessarily the same as the PDCCH region 222 and the PDSCH region 224 in the subframe 220 sent from the relay node 102. To distinguish between these regions, the PDCCH region 212 and the PDSCH region 214 in the subframe 210 will hereinafter be referred to as the access node PDCCH region 212 and the access node PDSCH region 214, respectively. The PDCCH region 222 and the PDSCH region 224 in the subframe 220 will hereinafter be referred to as the relay node PDCCH region 222 and the relay node PDSCH region 224, respectively.

The relay node 102 is configured to send the information in the relay node PDCCH region 222 to the UA 110 at approximately the same time that the access node 106 is sending the information in the access node PDCCH region 212 to the relay node 102. In the example of FIG. 2 a, the relay node PDCCH region 222 is larger than the access node PDCCH region 212. For example, the relay node PDCCH region 222 might consist of two OFDM symbols, while the access node PDCCH region 212 might consist of only one OFDM symbol.

Since the relay node 102 cannot receive the information in the access node PDCCH region 212 while it is transmitting the information in the relay node PDCCH region 222, the relay node 102 does not receive any information regarding the size of the access node PDCCH region 212. The relay node 102 simply begins listening for the data in the access node PDSCH region 214 at the point 230 where the relay node 102 finishes sending the information in the relay node PDCCH region 222. However, the access node 106 actually began transmitting the data in the access node PDSCH region 214 at the point 240 where the access node 106 finished sending the information in the access node PDCCH region 212. That is, the access node 106 began sending the data in the access node PDSCH region 214 before the relay node 102 began listening for the data in the access node PDSCH region 214. This causes the relay node 102 to miss a portion 250 of the data in the access node PDSCH region 214.

FIG. 2 b illustrates another scenario. In this case, the relay node PDCCH region 222 is smaller than the access node PDCCH region 212. For example, the relay node PDCCH region 222 might consist of two OFDM symbols, while the access node PDCCH region 212 might consist of three OFDM symbols. The relay node 102 again begins listening for the data in the access node PDSCH region 214 at the point 230 where the relay node 102 completes transmitting the information in the relay node PDCCH region 222. In this scenario, however, the access node 106 is still transmitting PDCCH information at point 230. Therefore, the relay node 102 will begin listening for PDSCH data before any PDSCH data is being transmitted. The relay node 102 might be able to ignore the portion 260 of PDCCH information that is received when PDSCH data is expected, but listening for and decoding this information may be a waste of resources.

In yet another scenario (not shown), the relay node PDCCH region 222 and the access node PDCCH region 212 are the same size. In this case, the relay node 102 will begin listening for the data in the access node PDSCH region 214 at approximately the same time that the access node 106 begins transmitting the data in the access node PDSCH region 214. However, due to relay switching delays as the relay node 102 changes from a transmission mode to a reception mode, the relay node 102 might still miss a portion of the PDSCH data.

In various embodiments, the access node 106 informs the relay node 102 when to start listening for PDSCH data. In one embodiment, the size of the access node PDCCH region 212 is fixed, the access node 106 informs the relay node 102 of this size, and the relay node 102 starts listening for PDSCH data at the fixed endpoint of the PDCCH information. In another embodiment, the size of the access node PDCCH region 212 is variable, and the access node 106 informs the relay node 102 to start listening for PDSCH data at a point that is beyond the endpoint of the largest possible access node PDCCH region.

FIG. 3 a illustrates the first of these embodiments. In this case, the size of the access node PDCCH region 212 is fixed in the subframes in which the access node 106 transmits data to the relay node 102, for example, in the Multicast/Broadcast Single Frequency Network (MBSFN) subframes. This can be contrasted with the cases in FIGS. 2 a and 2 b and with subframes other than MBSFN subframes, where the access node PDCCH region 212 is dynamic and could possibly change from subframe to subframe.

For example, the access node PDCCH region 212 might be set to two OFDM symbols for every subframe that the access node 106 sends to the relay node 102. In other cases, other sizes of the access node PDCCH region 212 could be set. The access node 106 can transmit the size of the access node PDCCH region 212 to the relay node 102 in high layer signaling 310. That is, this size information is not transmitted in the PDCCH. For example, the access node 106 might transmit the size information in the broadcast control channel (BCCH), in radio resource control (RRC) signaling, as a media access control (MAC) control element, or in some other high layer signal 310.

Another possibility is that this size information is pre-configured or preset to, for example, two or three OFDM symbols. In this case, no signaling is needed. In this embodiment, the size of the access node PDCCH region 212 is not less than the size of the relay node PDCCH region 222. For example, if the relay node PDCCH region 222 is two OFDM symbols, the size of the access node PDCCH region 212 would be no less than two OFDM symbols.

Upon learning the size of the access node PDCCH region 212, the relay node 102 knows the fixed point 320 at which the access node 106 will stop sending PDCCH information and begin sending PDSCH data. The relay node 102 then knows to begin listening for PDSCH data from the access node 106 at a corresponding point 330.

In some cases, the access node 106 might indicate a size that is slightly smaller than the actual size of the access node PDCCH region 212. This can cause the relay node 102 to begin listening for PDSCH data at a time slightly before the PDSCH data actually starts to be transmitted. This, in turn, can compensate for any relay switching delays and prevent the relay node 102 from missing any PDSCH data that might be sent while the relay node 102 is in transition from a transmitting mode to a receiving mode.

Alternatively, the access node 106 might send the relay node 102 the actual size of the access node PDCCH region 212, but the relay node 102 might begin listening for PDSCH data at a point 330 that is slightly before the point 320 when the access node PDCCH region 212 ends. This could again compensate for switching delays and ensure that the relay node 102 receives all of the PDSCH data.

FIG. 3 b illustrates an alternative embodiment. In this case, the sizes of the access node PDCCH region 212 and the access node PDSCH region 214 are flexible. If one of the regions becomes larger, the other region becomes correspondingly smaller, with the sum of their sizes remaining equal to the size of the subframe 210. Although these data region sizes can vary, the point at which the access node 106 begins transmitting relevant PDSCH data to the relay node 102 is fixed. In an embodiment, the access node 106 begins transmitting PDSCH data at a fixed point 340 that occurs after the latest point 320 at which the access node 106 could transmit PDCCH data.

For example, if the size of the access node PDCCH region 212 could vary in a range from one to four OFDM symbols, the access node 106 might begin transmitting PDSCH data at the fifth or sixth OFDM symbol of the subframe 210. If the size of the access node PDCCH region 212 could vary in a range from one to three OFDM symbols, the access node 106 might begin transmitting PDSCH data at the fourth or fifth OFDM symbol of the subframe 210, and so on. The access node 106 knows the latest possible endpoint for the variable-length PDCCH information and begins transmitting relevant PDSCH data to the relay node 102 at a fixed point beyond this endpoint.

The access node 106 can use high layer signaling 310, as described above, to inform the relay node 102 of the point 340 where the access node 106 will begin transmitting PDSCH data. The relay node 102 can then begin listening for the PDSCH data at a corresponding point 330. Similar to the embodiment described above, in order to compensate for switching delay, either the access node 106 or the relay node 102 might create a slight offset between the point 330 where the relay node begins listening for PDSCH data and the point 340 where the access node begins sending PDSCH data.

In this embodiment, a gap may exist between the point 320 where the access node 106 stops transmitting PDCCH information and the point 340 where the access node 106 begins transmitting actual PDSCH data. In an embodiment, the access node 106 has the capability to fill in this gap with dummy data 350. That is, the PDCCH region 212 still ends at point 320 and the PDSCH region 214 still begins at point 320. However, the portion of the PDSCH region 214 between point 320 and point 340 contains dummy PDSCH data 350 that is irrelevant to the relay node 102. Transmission of actual PDSCH data that is relevant to the relay node 102 does not begin until point 340.

FIG. 4 illustrates an embodiment of a method 400 for informing a relay node when to receive data. In block 410, the relay node is informed of a fixed point in a subframe of data when an access node will begin transmitting relevant data over a physical downlink shared channel. In block 420, the relay node begins to receive data at approximately the fixed point.

The UA 110 and other components described above might include a processing component that is capable of executing instructions related to the actions described above. FIG. 5 illustrates an example of a system 1300 that includes a processing component 1310 suitable for implementing one or more embodiments disclosed herein. In addition to the processor 1310 (which may be referred to as a central processor unit or CPU), the system 1300 might include network connectivity devices 1320, random access memory (RAM) 1330, read only memory (ROM) 1340, secondary storage 1350, and input/output (I/O) devices 1360. These components might communicate with one another via a bus 1370. In some cases, some of these components may not be present or may be combined in various combinations with one another or with other components not shown. These components might be located in a single physical entity or in more than one physical entity. Any actions described herein as being taken by the processor 1310 might be taken by the processor 1310 alone or by the processor 1310 in conjunction with one or more components shown or not shown in the drawing, such as a digital signal processor (DSP) 1380. Although the DSP 1380 is shown as a separate component, the DSP 1380 might be incorporated into the processor 1310.

The processor 1310 executes instructions, codes, computer programs, or scripts that it might access from the network connectivity devices 1320, RAM 1330, ROM 1340, or secondary storage 1350 (which might include various disk-based systems such as hard disk, floppy disk, or optical disk). While only one CPU 1310 is shown, multiple processors may be present. Thus, while instructions may be discussed as being executed by a processor, the instructions may be executed simultaneously, serially, or otherwise by one or multiple processors. The processor 1310 may be implemented as one or more CPU chips.

The network connectivity devices 1320 may take the form of modems, modem banks, Ethernet devices, universal serial bus (USB) interface devices, serial interfaces, token ring devices, fiber distributed data interface (FDDI) devices, wireless local area network (WLAN) devices, radio transceiver devices such as code division multiple access (CDMA) devices, global system for mobile communications (GSM) radio transceiver devices, worldwide interoperability for microwave access (WiMAX) devices, and/or other well-known devices for connecting to networks. These network connectivity devices 1320 may enable the processor 1310 to communicate with the Internet or one or more telecommunications networks or other networks from which the processor 1310 might receive information or to which the processor 1310 might output information. The network connectivity devices 1320 might also include one or more transceiver components 1325 capable of transmitting and/or receiving data wirelessly.

The RAM 1330 might be used to store volatile data and perhaps to store instructions that are executed by the processor 1310. The ROM 1340 is a non-volatile memory device that typically has a smaller memory capacity than the memory capacity of the secondary storage 1350. ROM 1340 might be used to store instructions and perhaps data that are read during execution of the instructions. Access to both RAM 1330 and ROM 1340 is typically faster than to secondary storage 1350. The secondary storage 1350 is typically comprised of one or more disk drives or tape drives and might be used for non-volatile storage of data or as an over-flow data storage device if RAM 1330 is not large enough to hold all working data. Secondary storage 1350 may be used to store programs that are loaded into RAM 1330 when such programs are selected for execution.

The I/O devices 1360 may include liquid crystal displays (LCDs), touch screen displays, keyboards, keypads, switches, dials, mice, track balls, voice recognizers, card readers, paper tape readers, printers, video monitors, or other well-known input/output devices. Also, the transceiver 1325 might be considered to be a component of the I/O devices 1360 instead of or in addition to being a component of the network connectivity devices 1320.

In an embodiment, a method is provided for informing a relay node when to receive data. The method includes the relay node being informed of a fixed point in a subframe of data when an access node will begin transmitting relevant data over a physical downlink shared channel. The method further includes the relay node beginning to receive data at approximately the fixed point.

In another embodiment, an access node in a wireless telecommunications system is provided. The access node includes a processor configured such that the access node transmits to a relay node information related to a fixed point in a subframe of data at which the access node will begin transmitting relevant physical downlink shared channel data.

In another embodiment, a relay node in a wireless telecommunications system is provided. The relay node includes a processor configured such that the relay node receives from an access node information related to a fixed point in a subframe of data at which the access node will begin transmitting relevant physical downlink shared channel data. The processor is further configured to begin to receive data at approximately the fixed point.

The following are incorporated herein by reference for all purposes: 3rd Generation Partnership Project (3GPP) Technical Specification (TS) 36.813 and 3GPP TS 36.814.

While several embodiments have been provided in the present disclosure, it should be understood that the disclosed systems and methods may be embodied in many other specific forms without departing from the scope of the present disclosure. The present examples are to be considered as illustrative and not restrictive, and the intention is not to be limited to the details given herein. For example, the various elements or components may be combined or integrated in another system or certain features may be omitted, or not implemented.

Also, techniques, systems, subsystems and methods described and illustrated in the various embodiments as discrete or separate may be combined or integrated with other systems, modules, techniques, or methods without departing from the scope of the present disclosure. Other items shown or discussed as coupled or directly coupled or communicating with each other may be indirectly coupled or communicating through some interface, device, or intermediate component, whether electrically, mechanically, or otherwise. Other examples of changes, substitutions, and alterations are ascertainable by one skilled in the art and could be made without departing from the spirit and scope disclosed herein. 

1. A method for informing a relay node when to receive data, comprising: the relay node being informed of a fixed point in a subframe of data when an access node will begin transmitting relevant data over a physical downlink shared channel (PDSCH); and the relay node beginning to receive data at approximately the fixed point.
 2. The method of claim 1, wherein the relevant data includes at least a relay physical downlink control channel (R-PDCCH).
 3. The method of claim 1, wherein the access node informs the relay node of the fixed point via high layer signaling.
 4. The method of claim 3, wherein the high layer signaling is at least one of: a broadcast control channel; radio resource signaling; and a media access control (MAC) control element.
 5. The method of claim 1, wherein the fixed point is pre-configured or preset.
 6. The method of claim 5, wherein the fixed point is at a fourth or fifth OFDM symbol of the subframe.
 7. The method of claim 1, wherein the size of a physical downlink control channel (PDCCH) region in the subframe is fixed, and wherein the fixed point is approximately the endpoint of the PDCCH region.
 8. The method of claim 1, wherein the size of a physical downlink control channel (PDCCH) region in the subframe is variable, and wherein the fixed point occurs no earlier than the endpoint of the largest possible PDCCH region.
 9. The method of claim 8, wherein the access node inserts dummy data into the portion of the subframe between the endpoint of the PDCCH region and the fixed point.
 10. The method of claim 1, wherein the relay node begins receiving data at a time before the fixed point.
 11. An access node in a wireless telecommunications system, comprising: a processor configured such that the access node transmits to a relay node information related to a fixed point in a subframe of data at which the access node will begin transmitting relevant physical downlink shared channel (PDSCH) data.
 12. The access node of claim 11, wherein the relevant data includes at least a relay physical downlink control channel (R-PDCCH).
 13. The access node of claim 11, wherein the access node transmits the information related to the fixed point via high layer signaling.
 14. The access node of claim 13, wherein the high layer signaling is at least one of: a broadcast control channel; radio resource signaling; and a media access control (MAC) control element.
 15. The access node of claim 11, wherein the fixed point is pre-configured or preset.
 16. The access node of claim 15, wherein the fixed point is at a fourth or fifth OFDM symbol of the subframe.
 17. The access node of claim 11, wherein the size of a physical downlink control channel (PDCCH) region in the subframe is fixed, and wherein the fixed point is approximately the endpoint of the PDCCH region.
 18. The access node of claim 11, wherein the size of a physical downlink control channel (PDCCH) region in the subframe is variable, and wherein the fixed point occurs no earlier than the endpoint of the largest possible PDCCH region.
 19. The access node of claim 18, wherein the access node inserts dummy data into the portion of the subframe between the endpoint of the PDCCH region and the fixed point.
 20. The access node of claim 11, wherein the access node informs the relay node to begin receiving data at a time before the fixed point.
 21. A relay node in a wireless telecommunications system, comprising: a processor configured such that the relay node receives from an access node information related to a fixed point in a subframe of data at which the access node will begin transmitting relevant physical downlink shared channel (PDSCH) data, and further configured to begin to receive data at approximately the fixed point.
 22. The relay node of claim 21, wherein the relevant data includes at least a relay physical downlink control channel (R-PDCCH).
 23. The relay node of claim 21, wherein the relay node receives the information related to the fixed point via high layer signaling.
 24. The relay node of claim 23, wherein the high layer signaling is at least one of: a broadcast control channel; radio resource signaling; and a media access control (MAC) control element.
 25. The relay node of claim 21, wherein the fixed point is pre-configured or preset.
 26. The relay node of claim 25, wherein the fixed point is at a fourth or fifth OFDM symbol of the subframe.
 27. The relay node of claim 21, wherein the size of a physical downlink control channel (PDCCH) region in the subframe is fixed, and wherein the fixed point is approximately the endpoint of the PDCCH region.
 28. The relay node of claim 21, wherein the size of a physical downlink control channel (PDCCH) region in the subframe is variable, and wherein the fixed point occurs no earlier than the endpoint of the largest possible PDCCH region.
 29. The relay node of claim 28, wherein the portion of the subframe between the endpoint of the PDCCH region and the fixed point contains dummy data.
 30. The relay node of claim 21, wherein the relay node begins receiving data at a time before the fixed point. 